Db reconfig #10
Merged
Db reconfig #10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RodrigoACG
approved these changes
Sep 12, 2024
clydeautin
approved these changes
Sep 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Change
Describe Changes Made
In this PR I reconfigured our DB SChema. The Prior way had no association between users and there created events. also the naming convention of the many to many table of users sign up for or "attending" the event created conflicts for our user to event association, now we can have a nested controller under users for users events.
I went ahead and set up routes and controllers with notes so its a easy to follow transition.
Testing will have to get sorted out for the old joins table.
PR Checklist